Address/command chip controlled data chip address sequencing for a distributed memory buffer system

ABSTRACT

One or more memory systems, architectural structures, and/or methods of storing information in memory devices is disclosed to improve the data bandwidth and or to reduce the load on the communication links. The system may include one or more memory devices, one or more memory control circuits and one or more data buffer circuits. The memory system, architectural structure and/or method improves the ability of the communications links to transfer data downstream to the data buffer circuits. In one aspect, the memory control circuit receives a store command and a store data tag (Host tag) from a Host and sends the store data command and the store data tag to the data buffer circuits. No store data tag or control signal is sent over the communication links between the Host and the data buffer circuits, only data is sent over the communication links between the Host and the data buffer circuits.

BACKGROUND

The present invention relates to memory systems and more particularlydistributed buffer memory systems.

With recent advancement of information technology and wide use of theInternet to store and process information, more and more demands areplaced on the acquisition, processing, storage and dissemination ofinformation by computing systems. Computing systems are being developedto increase the speed at which the computers are able to executeincreasingly complex applications for business, personal use, andentertainment. Overall computer system performance is affected by eachof the key elements of the computer structure, including theperformance/structure of the processors, any memory caches, input/output(I/O) subsystems, efficiency of the memory control functions, theperformance of the memory devices and systems, and any associated memoryinterface elements, and the type and structure of the memoryinterconnect interfaces.

The constantly increasing speed of processors which execute increasinglycomplex applications places more rigorous performance demands on all ofthe other subsystems in the computer, including the memory subsystem,where data is stored, accessed, and updated numerous times during theoperation of a software application. The time consumed by memoryread/write operations is a major factor in the ultimate speed andefficiency of a computer system. The memory subsystem of most computersis normally operated by a memory controller. The task of memorycontrollers is to move data between the computer's memory subsystem andits one or more processors as quickly and efficiently as possible. Acomputer's memory subsystem often comprises memory modules, usually oneor more dual in-line memory modules (DIMMs) that include several dynamicrandom access memory (DRAM) devices.

In many memory subsystems, a memory controller may control multiplememory channels, where each channel may include one or more Dual In-lineMemory Modules (DIMMs), where the DIMMs may be arranged in one or moreranks. Computing demands require the ability to access an increasingnumber of higher density memory devices at faster and faster accessspeeds.

Extensive research and development efforts are invested by the industryto create improved and or innovative solutions to maximize overallsystem performance by improving the memory system/subsystem designand/or structure and the methods by which the memory system/subsystemoperates. Such efforts have resulted in the development of distributedmemory systems, distributed buffer memory systems, registered DIMMs(RDIMMs) and load reduced DIMMs (LRDIMMs), and other systems,specifications and standards such as, for example, DDR4 and DDR5, whichprovide for increased memory performance.

In one example, a distributed memory system may include a plurality ofmemory devices, one or more Address Chips (AC), also known as memorycontrol circuits, and a plurality of data buffer or data (DC) circuits.There are communication links or buses between a Host processor and thememory control circuits and data buffer circuits. There is also acommunication link or bus from the memory control circuits to the databuffer circuits. There are also communication links between the memorydevices, e.g., DRAMS, and the memory control circuits and the databuffer circuits. Bandwidth limitations on communication links can affectperformance of memory systems. The amount of data, command, control andresponse signals sent over communication links and busses between theHost, the memory control circuits, the data buffer circuits, and thememory devices, which includes the bandwidth allocated to transmit storedata control functions, e.g., store data address tags and locations,impacts performance of memory systems.

SUMMARY

The summary of the disclosure is given to aid understanding of thememory system, architectural structure and method of storing andfetching data, and not with an intent to limit the disclosure or theinvention. The present disclosure is directed to a person of ordinaryskill in the art. It should be understood that various aspects andfeatures of the disclosure may advantageously be used separately in someinstances, or in combination with other aspects and features of thedisclosure in other instances. Accordingly, variations and modificationsmay be made to the memory systems, architectural structure and method ofoperation to achieve different effects.

A computer's memory subsystem often comprises memory modules, usuallyone or more dual in-line memory modules (DIMMs), which usually include aplurality of memory devices, e.g., dynamic random access memory (DRAM)devices. A distributed memory system may include a plurality of memorydevices, e.g., DRAMS, which may be arranged on a module as a DIMM, oneor more memory control circuits, and one or more data buffer circuits ordata circuits. In one embodiment, the memory control circuit receivessignals from a Host processor and outputs command and control signals.The memory control circuit may include a memory controller, and in oneembodiment, may have a scheduler, which may be in the form of a circuit.The memory control circuit and/or memory controller in one embodimentmay be remote from the Host processor, the data buffer circuits, and/orthe memory devices. The memory control circuit, e.g., the scheduler, mayoptimize the order of operations and instructions, and sends out commandsignals (e.g., instructions) to the data buffer circuits and the memorydevices. There are communication links or buses between the Host (e.g.,processor), the memory control circuits, and the data buffer circuits,and/or the memory devices. In one embodiment, there is a communicationbus or link from the memory control circuit to the data buffer circuits.In one embodiment there may also be communication buses and linksbetween the Host and the memory control circuit, and separatecommunication buses or links between Host and the data buffer circuits.The memory system and/or architectural structure may further include acommunication link or bus between the memory devices and the memorycontrol circuit, and/or the data buffer circuit.

In one embodiment, a memory system, architectural structure, and/ormethod of storing information is disclosed to improve the data bandwidthbetween the Host and the data buffer circuits. In one embodiment, amemory system, architectural structure, and/or method to store writedata in a data buffer circuit is described which improves the databandwidth between the Host and data buffer circuit. In an embodiment, amemory system, architectural structure and/or method of storinginformation or data is disclosed where the Host sends the write buffertag to the memory control circuit and the AC sends the write buffer tagto all the DC chips. In one embodiment the Host sends and only thememory control circuit receives from the Host the store data tag, andthe Host sends the data to the data buffer circuits after a configurableor programmable delay. In an embodiment of a memory system,architectural structure, and/or method of storing data, the memorycontrol circuit receives the store command from the Host and the memorycontrol circuit sends a write-to-buffer command and store data tag toall the data buffer circuits, but no write to buffer tag is sent overthe downstream link between the Host and the data buffer circuits. Inone embodiment, the memory system, architectural structure and/or methodof storing information and data includes a distributed memory systemhaving a module containing a memory control circuit, a plurality of databuffer circuits, and a plurality of memory devices, and in one examplemay contain one AC chip, nine data chips, and a plurality of memorydevice chips arranged or organized in groups, preferably in groups ofnine (e.g., 9, 18, 27, 36, etc.) or ten (e.g., 10, 20, 30, 40, etc.),preferably as a DIMM.

In one embodiment, a memory system for storing data in response tocommands received from a Host is disclosed, the memory systemcomprising: a memory control circuit to receive commands from the Hostand to output module command and control signals; at least one memorydevice configured to store data and receive command signals from thememory control circuit; at least one data buffer circuit associated withthe at least one memory device; a communications link for communicatingdata between the Host and the at least one memory device, wherein thecommunications link includes a data communications link between the Hostand the at least one data buffer circuit, and the at least one databuffer circuit and the at least one memory device, and only data istransmitted on the data communications link between the at least onedata buffer circuit and the Host; and a control communications linkbetween the memory control circuit and the at least one data buffercircuit, wherein the memory control circuit is configured to: (i) inresponse to receiving the Host store command, decode the store commandinto a write-to-buffer command and store-from-buffer command; and (ii)send the write-to-buffer command and a store data tag to the data buffercircuit over the control communications link, wherein the store data tagspecifies the location to store the data into the at least one databuffer circuit. In one embodiment, no store data tag is sent to the atleast one data buffer circuit over the communication link between theHost and the at least one data buffer circuit. In accordance with oneaspect, the at least one data buffer circuit is configured to inresponse to receiving a write-to-buffer command, push incoming storedata into the data buffer pointed to by the store data tag received fromthe memory control circuit. The incoming store data may be pushed intothe at least one data buffer circuit after a configurable delay.

In one embodiment, the memory control circuit is configured to send astore command to the at least one memory device, the store commandcomprising a command and an address location to store the data in thememory devices. The memory control circuit preferably is furtherconfigured to send the store-from-buffer command along with store datatag to the at least one data buffer circuit. The store-from-buffercommand and store data tag are sent to the at least one data buffercircuit in one configuration over a BCOM link between the memory controlcircuit and the data buffer circuit. The data buffer circuit may befurther configured to pull store data from the data buffer locationpointed to by the store data tag received from the memory controlcircuit over the control communications link and send the store data tothe at least one memory device. The system in one aspect furthercomprises at least one module having the memory circuit formed on asingle chip, a group of nine or ten data buffer circuits formed onseparate chips and arranged on the module, and a plurality of memorydevices arranged in groups of nine or ten chips on the module.

In accordance with another embodiment a memory system for reading andwriting data to a memory device is disclosed, the system comprising: atleast one memory control circuit to receive commands from a Host and tooutput command and control signals; at least one memory deviceconfigured to read and store data, and receive command signals from thememory control circuit; at least one data buffer circuit associated withthe at least one memory control circuit; a data communications link forcommunicating data between the Host and the at least one memory device,wherein the data communications link includes a communications linkbetween the Host and the at least one data buffer circuit, and the atleast one data buffer circuit and the at least one memory device, andonly data is transmitted on the communications link between the at oneleast data buffer circuit and the Host; and a control communicationslink between the at least one memory control circuit, the at least onememory device, and the at least one data buffer circuit for transmittingreading and writing operation signals of the memory system; wherein theat least one memory control circuit is configured to: (i) decode a storecommand into a write-to-buffer command and a store-from-buffer command;(ii) send the write-to-buffer command along with the store data tag tothe at least one data buffer circuit; (iii) send a store command to theat least one memory device; and (iv) send the store-from-buffer commandalong with store data tag to the at least one data buffer circuit, andwherein the at least one data buffer circuit is configured to: (i) sendincoming store data into a local data buffer pointed to by the localstore data tag obtained by the memory control circuit; (ii) pull outstore data from the local data buffer pointed to by store data tagreceived from the at least one memory control circuit; and (iii) sendstore data to the at least one memory device. In one aspect, thewrite-to-buffer command and the store data tag are configured to be sentto the data buffer circuit over the communication link between thememory control circuit and the data buffer circuit. The store data tagthat is sent to the at least one data buffer circuit in oneconfiguration is not sent over the data communications link between theHost and the at least one data buffer circuit.

The system according to one embodiment is configured to send thestore-from-buffer command and store data tag to the data buffer circuitover the link between the memory control circuit and the at least onedata buffer circuit. The system is preferably configured and adapted sothat the at least one data buffer circuit receives its store data tagover the link between the memory control circuit and the at least databuffer circuit, and the store data is sent to the at least one memorydevice from the at least one data buffer circuit via the link betweenthe at least one data buffer circuit and the at least one memory device.

In another aspect, a method for storing data in memory devices isdisclosed, the method comprising: (i) obtaining a store command andstore data tag from a host; (ii) processing the store command in amemory control circuit into a write-to-buffer command and astore-from-buffer command; (iii) sending the write-to-buffer command anda store data tag from the memory control circuit to at data buffercircuit; and (iv) pushing incoming data into the location in the databuffer circuit pointed to by the store data tag obtained from the memorycontrol circuit. In accordance with another embodiment, the data buffercircuit pushes incoming data into the data buffer circuit upon receivingthe write-to-buffer command. The data buffer circuit in one embodimentreceives the data over the link between the host and the data buffercircuit, but no store data tag is received by the data buffer circuitfrom the host over the link between the host and the data buffercircuit. The method in one aspect further comprising sending a storecommand from the memory control circuit to the memory devices; sendingthe store-from-buffer command along with the store data tag to the databuffer circuit; and sending data from the location pointed to by thestore data tag obtained from the memory control circuit to the memorydevices. The data buffer circuit in a further aspect receives the datastore tag over the link between the memory control circuit and the databuffer circuit. The method may further comprises the step of pushing thestore data tag back to the host.

In yet another embodiment, a computer program product for storing datain a memory device is disclosed, the computer program product comprisinga computer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a memory system tocause the memory system to perform a method, the memory systempreferably as described in connection with FIG. 4 comprising a memorycontrol circuit, one or more data buffer circuits and a plurality ofmemory devices, the method comprising: (i) processing a store command ina memory control circuit into a write-to-buffer command and astore-from-buffer command; (ii) sending the write-to-buffer command andthe local store data tag from the memory control circuit to the databuffer circuits and not sending any control signal to the data buffercircuits directly from the Host; and (iii) pushing incoming data intothe location in the data buffer circuits pointed to by the store datatag obtained from the memory control circuit. In one aspect of thecomputer program product, the data buffer circuits push incoming datainto the data buffer circuits upon receiving the write-to-buffercommand. In a further aspect of the computer program product, the databuffer circuits receive the data over the link between the Host and thedata buffer circuits, but no store data tag is received from the Hostover the link between the Host and the data buffer circuits. In oneembodiment of the computer program product, the method furthercomprising sending a store command from the memory control circuit tothe memory devices; sending the store-from-buffer command along with thestore data tag to the data buffer circuits; and sending data from thelocation pointed to in the data buffer circuits by the store data tag;and sending the store data tag obtained from the memory control circuitto the memory devices. In another aspect of the computer program productthe data buffer circuit receives the data store tag over the linkbetween the memory control circuit and the data buffer circuit. In afurther aspect of the computer program product, the method furthercomprising the step of pushing the store data tag back to the host.

BRIEF DESCRIPTION OF THE DRAWINGS

The various aspects, features and embodiments of the memory system,architectural structure and its method of operation will be betterunderstood when read in conjunction with the figures provided.Embodiments are provided in the figures for the purpose of illustratingaspects, features and/or various embodiments of the memory system,architectural structure and method of operation, but the claims shouldnot be limited to the precise arrangement, structures, features,aspects, embodiments or devices shown, and the arrangements, structures,subassemblies, features, aspects, embodiments, methods, and devicesshown may be used singularly or in combination with other arrangements,structures, subassemblies, features, aspects, embodiments, methods anddevices.

FIG. 1 depicts a general computing or data processing system inaccordance with one embodiment.

FIG. 2 depicts a memory subsystem in accordance with an embodiment.

FIG. 3 depicts a memory subsystem including a buffered DIMMconfiguration in accordance with an embodiment.

FIG. 4 diagrammatically depicts a distributed buffer memory system inaccordance with one embodiment.

FIG. 5 shows the command and address frame sent over a communicationslink between the Host and a memory control circuit in accordance withone embodiment.

FIG. 6 shows a data frame sent over a communications link from Host to adata buffer circuit in accordance with an embodiment.

FIG. 7 shows a frame sent over a communications link from a memorycontrol circuit to the Host in accordance with one embodiment.

FIG. 8 depicts a flow diagram of a method of performing a storeoperation in accordance with one embodiment.

DETAILED DESCRIPTION

The following description is made for illustrating the generalprinciples of the invention and is not meant to limit the inventiveconcepts claimed herein. In the following detailed description, numerousdetails are set forth in order to provide an understanding of the memorysystem, architectural structure and method of operation, however, itwill be understood by those skilled in the art that different andnumerous embodiments of the memory system, architectural structure andmethod of operation may be practiced without those specific details, andthe claims and invention should not be limited to the embodiments,subassemblies, features, processes, methods, aspects, features ofdetails specifically described and shown herein. Further, particularfeatures described herein can be used in combination with otherdescribed features in each of the various possible combinations andpermutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc. It must also benoted that, as used in the specification and the appended claims, thesingular forms “a,” “an” and “the” include plural referents unlessotherwise specified.

Memory systems, memory architecture, and/or methods of performingread/write operations in a memory system or subsystem, including, forexample, a distributed memory system, are disclosed. In one embodiment,a memory system, architectural structure, and/or method of storingand/or fetching data in memory systems, including memory devices, isdisclosed. The memory system as disclosed in more detail below mayinclude one or more memory devices, and one or more data buffercircuits. The memory system may further include a memory controlcircuit, which may in one embodiment include a memory controller tocontrol the flow of data going to and from the memory devices. There maybe communication links or buses for transferring data, commands,responses, and/or signals between the Host, the memory devices, the databuffer circuits, and/or the memory control circuits.

In one aspect, the memory system, architectural structure, and/or methodfor performing read/write operations improves the data bandwidth on thecommunication link between the Host and data buffer circuits. In oneembodiment, a memory system, architectural structure, and/or method ofstoring write data to the data buffer circuit is disclosed. In oneaspect, a memory system, architectural structure and/or method ofmanaging store data at the data buffer circuit is disclosed. In oneembodiment, the disclosure provides a system, architectural structure,and/or method for the data buffer circuits to put store data into theirwrite buffer. In one aspect, a memory system, architectural structure,and/or method is disclosed where the Host sends the store data tag tothe memory control circuit.

In one embodiment, a memory system, architectural structure, and/ormethod to store write data in a data buffer circuit is described whichimproves the data bandwidth between the Host and data buffer circuit. Inan embodiment, a memory system, architectural structure and/or method ofstoring information or data is disclosed where the Host sends the writebuffer tag to the memory control circuit and the AC sends the writebuffer tag to all the DC chips. In one embodiment the Host sends andonly the memory control circuit receives from the Host the store datatag, and the Host sends the data to the data buffer circuits after aconfigurable or programmable delay. In an embodiment of a memory system,architectural structure, and/or method of storing data, the memorycontrol circuit receives the store command from the Host and the memorycontrol circuit sends a write-to-buffer command and store data tag toall the data buffer circuits, but no write to buffer tag is sent overthe downstream link between the Host and the data buffer circuits. Inone embodiment, the memory system, architectural structure and/or methodof storing information and data includes a distributed memory systemhaving a module containing a memory control circuit, a plurality of databuffer circuits, and a plurality of memory devices, and in one examplemay contain one AC chip, nine data chips, and a plurality of memorydevice chips arranged in groups of nine (e.g., 9, 18, 27, 36, etc.)preferably as a DIMM.

A computing or data processing system 100 suitable for storing and/orexecuting program code may take many forms and in one embodiment mayinclude at least one processor 102, which may be or be part of acontroller, coupled directly or indirectly to memory devices or elementsthrough a system bus, as shown in FIG. 1. Computing system 100 in FIG. 1is shown with a processor 102, Random Access Memory (RAM) 103,nonvolatile memory 104, device specific circuits 101, and I/O interface105. Alternatively, the RAM 103 and/or nonvolatile memory 104 may becontained in the processor 102 as could the device specific circuits 101and I/O interface 105. The processor 102 may comprise, for example, anoff-the-shelf microprocessor, custom processor, Field Programmable GateArray (FPGA), Application Specific Integrated Circuit (ASIC), discretelogic, etc. The RAM 103 is typically used to hold variable data, stackdata, executable instructions, etc., and may include Dynamic RandomAccess Memory or DRAM.

According to various approaches, the nonvolatile memory 104 may compriseany type of nonvolatile memory such as, but not limited to, ElectricallyErasable Programmable Read Only Memory (EEPROM), flash Programmable ReadOnly Memory (PROM), battery backup RAM, hard disk drives, etc. Thenonvolatile memory 104 is typically used to hold the executable firmwareand any nonvolatile data containing programming instructions that can beexecuted to cause the processor 102 to perform certain functions.

In some embodiments, the I/O interface 105 may include a communicationinterface that allows the processor 102 to communicate with devicesexternal to the controller. Examples of the communication interface maycomprise, but are not limited to, serial interfaces such as RS-232, USB(Universal Serial Bus), Small Computer Systems Interface (SCSI), RS-422or a wireless communication interface such as Wi-Fi, Bluetooth,near-field communication (NFC) or other wireless interfaces. Thecomputing system 100 may communicate with an external device via thecommunication interface 105 in any communication protocol such asAutomation/Drive Interface (ADI).

FIG. 2 depicts an exemplary memory system 200 that may be part of alarger computer system structure or network. The computer system 200includes a control processor system 202, which is a processing subsystemthat includes at least one processor unit (CPU) 206 that may beconfigured to interface with a Memory Control Unit (MCU) 210. Theprocessor or CPU 206 may be a module that processes read, write, andconfiguration requests from a system controller (not depicted). Theprocessor 206 may be a multi-core processor. The MCU 210 may include amemory controller synchronous (MCS) 208, also referred to as a memorycontroller, that controls communication with one or more memory devices250 (not shown in FIG. 1) in a memory subsystem 220. The MCU 210 and theMCS 208 may include one or more processing circuits, or processing maybe performed by or in conjunction with the processor 206. The controlprocessor system 202 communicates with the memory subsystem 220 througha communications bus 215 as will be described in more detail inconnection with FIG. 4. Control processor system 202, processor or CPU206, memory control unit 210, and MCS 208, individually andcollectively, may be referred to herein as the Host. The Host as usedherein is used broadly to refer to a processor, controller or devicethat sends and receives command and/or control signals to a memorysystem or subsystem. The Host may also send and receive data signalsfrom a memory system or subsystem.

FIG. 3 depicts an example of a memory subsystem 320. Memory system 320comprises a plurality of memory modules, e.g., Dual Inline MemoryModules or DIMMs 325. While only three (3) DIMMs 325 a-c are shown inFIG. 3, it will be appreciated that memory subsystem 320 may containmore are less DIMMs 325. The DIMMs 325 may be arranged in channels andranks, with one or more DIMMs 325 per channel or rank. Each DIMM 325 maycontain one or more volatile memory devices, e.g., Dynamic Random AccessMemory chips or DRAMs 350. The memory devices 350 may be integratedcircuits or chips and form the basic memory cells that hold bits ofinformation. The memory cells in a memory device, e.g., DRAM, areusually arranged in banks, where each bank is an array of rows andcolumns.

The memory subsystem may also include one or more memory controlcircuits 330, one or more data buffer or data (DC) circuits or (DC)chips 340, and one or more memory devices 350. The memory controlcircuit manages the flow of data going to and from the memory devices.The memory control circuit typically receives signals such as commandand control signals from a Host, e.g., a Host processor. The controlsignals may include address locations or tags on where to store data inthe memory devices and/or data buffer circuits. The memory and controlcircuit may output command and control signals to the memory devices.The memory control circuits 330 for ease of reference may also bereferred to as address and command circuits, AC circuits or AC chips.The memory control circuit 330 may or may not have a Registered ClockDriver or RCD. The memory control circuit 330 in one embodiment may havea memory controller. The memory control circuit 330 or memory controller332 may have a scheduler 338. The memory control circuit 330, memorycontroller 332 and/or scheduler 338 may optimize the order of operationsand instructions, and sends out signals to the data buffer circuits andthe memory devices. The memory control circuit 330/memory controller332/memory scheduler 338 may reorder the sequence of operations. Thememory control circuit may or may not be located on the board or module,e.g., DIMM, with the memory devices. In embodiments, as shown in FIG. 3,the memory control circuits 330 are formed as an integrated circuit orchip and are located on the module 325 with the memory devices 350. Inone embodiment, the memory control circuit may be remote from the Hostprocessor.

The data buffer circuits 340 buffer, receive, transmit, and/or transferdata between the Host, e.g., control processor system 302, and thememory devices 350. The data buffer circuits may or may not be locatedon the same board or module, e.g., DIMM, as the memory devices and/orthe memory control circuits. The data buffer circuits 340 in oneembodiment are also formed as integrated circuits or chips and arelocated on the module 325 with the memory devices 350. The data buffercircuits may also be referred to as data circuits, DC circuits, and/orDC chips.

In the example of FIG. 3, a distributed memory system 300 is illustratedhaving a memory control processor 302 and/or memory control unit 310,and a memory subsystem 320. The memory control unit 310, and/or memorycontrol processor 302, may be a Host. The memory or data storage system320 may be configured to store data and to provide storage services toone or more Hosts, which can be connected to the storage system 320directly or through a network (e.g., over the internet). The storagesystem may include an interface for supporting communications with theHost.

In the embodiment of FIG. 3, the memory subsystem 300 has three (3)DIMMS 325 a-c. The distributed memory system 300 may have one or morecontrol processors systems or Hosts 302, and may have more or less DIMMs325. In the distributed memory system 300 of FIG. 3, each memory module325 is configured as a DIMM and has one memory control circuit or ACchip 330, nine (9) data buffer circuits or DC chips 340, and thirty-six(36) memory devices 350, e.g., DRAMs. The memory control circuit isconfigured and programmed to send command and control signals to thedata buffer circuits and the memory devices. Each memory control chip orAC chip 330 in this example manages the flow of data to and from thememory devices on the module 325. Each data buffer circuit or DC chip340 in this example interacts with and buffers data between four memorydevices 350. The DIMMs may include memory devices, e.g., DRAMs,preferably in groups of nine, e.g., 9, 18, 27, 36, etc.

Other configurations are contemplated for the memory module 325, and forthe memory subsystem 320. Typically there is one memory control chip 330per nine or ten data buffer chips 340. As an example, a DDR4 memorysystem may include a memory control circuit or AC chip and a group ofnine (9) data buffer circuits or DC chips. While the memory devicestructure and/or module of FIG. 3 shows the memory devices 350 in groupsof nine, it is contemplated that the memory devices may be arranged ingroups of ten or more. In the example of FIG. 3, one AC chip per DIMM isillustrated, although more AC chips per DIMM may be used. The memorysystem architecture may be formatted and structured to support DDR4 andDDR5 standards, although the methods, systems and architecture disclosedand taught would be applicable to other configurations, including futurestandards.

In one example, the data buffer circuits or DC chips 340 may each have awrite buffer array that is used to hold store operations from the Hostprocessor 302 (memory control unit 310) until the memory controller 332on the memory control circuit 330 can schedule them. There arecommunication buses or links between the Host 302 and the memory controlcircuit 330 and between the memory control circuit 330 and the memorydevices 350. There is also a data communications link or bus between theHost 302 and the data buffer circuits 340, and a communications link orbus between the data buffer circuits 340 and the memory devices 350.There may be a communication link or bus 332 from the memory controlcircuit 330 to the data buffer circuits or DC chips 340. Thecommunication link or bus between the memory control circuit 330 and thedata buffer circuits 340 may be a one way broadcast communication linkor bus called BCOM. More information on specific embodiments of thecommunication buses and links will be described below.

The bandwidth of the communication links impact performance of thememory system 300. In one or more embodiments, the memory system,architectural structure, and/or method of operation provide improvementsin storing and/or retrieving data between a Host and one or more memorydevices. In one embodiment, a memory system, architectural structure,and/or method is disclosed to improve the performance and/or bandwidthavailable for data on the communication link between the Host 302 andthe data buffer circuit or DC chip 340. In one embodiment, the bandwidthof the communications link between the Host 302 and the data buffercircuit 340 is improved by decreasing the frequency of (or eliminating)control information (tags) being sent from Host 302 to the data buffercircuit or DC chip 340 over the communications link between the Host 302and the data buffer circuit 340.

In one embodiment, the bandwidth of the downstream communications linkbetween the Host and the data buffer circuit 340 is improved by notsending write buffer tags over the link between the Host and the databuffer circuits and only sending data. To reduce demand on the linkbetween the Host and DC chips 340, in one embodiment of performing astore operation, the Host 300 sends a store command and store data tagto the memory control circuit (AC chip) 330, and the AC chip 330 sendsthe store data command to the DC chip 340, and a corresponding storedata tag to the DC chip 340. In one embodiment, the Host sends and theAC circuit receives a store command and a store data tag and the ACcircuit processes the store command into a write-to-buffer command and astore-from-buffer command, and sends the write-to-buffer command andstore data tag to the DC circuit; and also sends later, after thestore-from-buffer command is scheduled, the store-from-buffer commandand the same store data tag to the DC circuit. In one embodiment, theHost sends to only the AC chip the store data tag (Host does not sendstore data tag to the DC chip over the communications link between theHost and DC chip), which indicates where in the data buffer circuit tostore data, and the AC chip sends the store data tag to all the DC chipsover the communications link, e.g. a BCOM link, between the AC chip andthe DC chip, and the DC chip uses the store data tag to identify thelocation/address in the data buffer to store the incoming data from Host(sent to DC chips preferably after a programmable delay over thecommunications link between Host and DC chips).

FIG. 4 illustrates a schematic illustration of a distributed buffermemory system 400 according to one embodiment. The system includes aplurality of memory devices 450, e.g. DRAMs. The DRAMs may be arrangedon a module, usually a DIMM 325. The system 400 may have one or moreDIMMs. The system may further include one or more memory controlcircuits or AC chips 430, and one or more data buffer circuits or DCchips 440. In one embodiment, each DIMM may include one memory controlcircuit or AC chip 430 and a plurality of data buffer circuits or DCchips 440 (9 or 10 chips per AC chip). Each DIMM 325 may have memorydevices, e.g., DRAMs 450, arranged and configured in groups of nine,e.g., nine (9), eighteen (18), twenty-seven (27), thirty-six (36) ormore. The DIMMs may have an unequal number of memory devices, e.g.,DRAMs 450. In one embodiment, the system is designed to support DDR4 orDDR5 memory systems, although other configurations and arrangements arecontemplated. The memory control circuit 430 may or may not have aRegulated Clock Driver, and in one embodiment, the memory controlcircuit 430 may have a memory controller 432 and/or a memory scheduler438.

Link 460 diagrammatically illustrated in FIG. 4 is a differential HighSpeed Serial (HSS) bus with eight (8) lanes from the Host 402/410 to thememory control circuit or AC chip 430 for sending commands to the memorysubsystem 320 and one HSS lane back for reporting stats such asoperations that are complete, or error notification and detail. FIG. 5shows one example of the address and command frame sent over link 460from Host 402/410 to memory control circuit or AC chip 430. In FIG. 5,the address and command frame has two (2) bits (L0-L1) to specify thenumber of memory cycles to make up a frame; thirty-nine (39) bits ofaddressable space A0-A38; four (4) bits of space for commands (C0-C3);seven (7) bits Q0-Q6 for the tagfield match sent to the DC chips forwrite operations; one bit (ACK) for acknowledge for the upstream frame;and eleven (11) bits P0-P10 for Cyclic Redundancy Check (CRC) codeprovided for lane error isolation.

Link 465 is a HSS bus with two (2) lanes from the Host 402/410 to eachdata buffer circuit or DC chip 440 for store data and two (2) lanes fromeach DC chip 440 to the Host 402/410 for fetch data. For mainlineoperations, link 465 in an embodiment is used only for transmitting dataand the required cyclic redundancy check (CRC) for protecting that data.The bandwidth of link 465 in one embodiment is not consumed with anykind of control information and may not have any bandwidth consumed forresponse information. All two lanes of bandwidth for link 465 is used inan embodiment to transmit data (and CRC). FIG. 6 shows one example of adata frame for Host 402/410 to DC chip 440 communication over link 465.In FIG. 6, 128 bits (D0-D127 in memory cycles (frames) 1-8) are datafields; and sixteen (16) bits (CRC0-CRC15) in memory cycle (frame) 9) isfor CRC, so that nine (9) out of nine (9) or 100% of the bandwidth oflink 465 is used to transmit data and CRC. By not using link 465 fortransmitting control signals, e.g., tag or address locations, all nine(9) memory cycles are used for transmittal of data and CRC, whichimproves data transfer efficiency in link 465.

Link 470 is a broadcast (BCOM) bus from the memory control circuit or ACchip 430 to the data buffer circuits or DC chips 440 used to notify theDC chips when to execute the scheduled operations. For fetch operationsonly a command is sent over link 470 from the AC chip 430 to the DC chip440. According to one aspect, for store operations the control memorycircuit 430 processes, decodes, or cracks a store command into twosuboperations called “write buffer” or “write-to-buffer,” which writesdata from the Host 402/410 into the data buffer on the DC chips 440, and“store buffer” or “store-from-buffer,” which stores data from the DCchips 440 to the memory devices 450, e.g., DRAMs. For a write buffer, inone embodiment, a command is sent to the data buffer circuits or DCchips 440 from AC chip 430 over link 470, and a control signal, e.g., alocation tag address, is sent to the data buffer circuit. For a storebuffer operation, both a command and control signal, e.g., a writebuffer address, is sent to the data buffer circuit or DC chips 440.Operation of the memory subsystem will be described in more detailbelow.

There is also an Error ATTN network 475 between the memory controlcircuit 430 and the data buffer circuits or DC chips 440 that maytransmit an Error ATTN signal from the data buffer circuits or DC chips440 notifying the memory control circuit or AC chip 430 that a DC chip440 took an error that requires reporting to the Host 402/410. The ErrorATTN netework may be a wired OR open drain circuit. Note that the DRAMATTN signal that indicates a memory device 450, e.g., DRAM, took anerror is routed from the memory device 450 back to its DC chip 440instead of routing them directly back to the AC chip 430. The AC chip430 must report this error to the Host 402/410 since the DC chips 440have no response or control information in their upstream frame. The DCchip 440 forwards the memory device errors back to the AC chip 430 vialink 470, but each DC chip 440 has knowledge that one of its memorydevices, e.g., DRAMs 450, took an error. The AC chip 430 routes theerror signal back to the Host. The Host 402/410 may invoke its errorrecovery routine, and non-mainline operations from the Host 402/410 canbe used to read the status registers of the DC chips 440. The Host402/410 is then able to isolate which DC chip 440 took the error, if theerror occurred on the HSS link or was an ATTN from one of its memorydevices, or if it was some other error occurring on the DC chip 440. TheHost 402/410 may then take action as desired to recover from the error.

Link 480 is the command and address bus from the memory control circuitor AC chips 430 to the memory devices 450, e.g. DRAMs. Links 490 are thememory devices data buses used by the DC chip 440 to send store data tothe memory devices and receive fetch data from the memory devices 450.Communication link 490 also receives the memory device ATTN signal.

Turning now to the operation of a memory system, during normaloperations the Host 402/410 sends a store command to the memory controlcircuit or AC chip 430. The store command sent by the Host to the ACchip 430 may be processed, decoded, or cracked by the AC chip 430 into a“write buffer” command, which writes data from the Host into the databuffer on the DC chips 440, and a “store buffer” command, which storesdata from the DC chips 440 to the memory devices 450. The “write buffer”command is scheduled for execution right away, and the “store buffer”command is scheduled for execution by the memory control circuit basedon optimizing system performance.

The write buffer command is sent by the memory control circuit or ACchip 430 to the data buffer circuit or DC chips 440 over link 470 andthe Host 402/410 sends data to be stored to the DC chips 440 over link465, preferably after a configurable delay. In one embodiment, the ACchip sends an address, tag or location (e.g., a store data tag) to theDC chip 440 identifying where the store data should be located in thewrite buffer of the data buffer circuits 440. Each DC chip 440 can checkthe CRC codes from the store data received to verify that an error didnot occur over the HSS link 465. If an error is found to have occurred,the DC chip 440 notifies the AC chip 430 via the Error ATTN signal overlink 475 that an error has taken place and the error is recorded in theDC chip's status register 448.

The AC chip 430 may include a scheduler 438 that optimizes the order ofoperations and system instructions and sends out commands. The scheduler438 can reorder operations. The AC chip scheduler 438 may schedule the“store buffer” command when it is optimal for system performance toexecute that operation. Bank collisions, periodic operations, and fetchcommands can cause a store operation to be delayed to allow otheroperations to complete or execute ahead of it. Once the “store buffer”operation completes the store operation, the Host store command isconsidered complete, and the AC chip 430 sends an upstream frame to theHost via link 480 using as an example the format in FIG. 7 to indicatewhich operations completed.

In one embodiment, fetch operations start with the fetch command beingsent to the AC chip 430 via communications link 460 because there is noneed to send data ahead of time. Fetch operations may be prioritized inthe system and if the buses are available for use, a fetch operationwill bypass store operations in the queue to minimize latency. If,however, there are other pending fetch operations that need to bescheduled, the fetch operation will enter the memory control circuitscheduler 438.

Once the memory control circuit memory scheduler 438 schedules the fetchoperation to execute, the command signal and control signal, e.g.,address (tag), is sent from the AC chip 430 over link 480 to the memorydevices 450 and the DC chips 440 are informed by the AC chip 430 overlink 470 that fetch data will arrive to be sent to the Host 402/410 in afixed number of cycles. Once the fetch data arrives at the DC chips 440,the data is forwarded directly to the Host 410/402 over link 465. Fetchdata preferably is not buffered as this would create additional latency.The AC chip 430 will then send an upstream frame to the Host notifyingit that the fetch operation has completed.

The response frame indicating which operations are completed is shown inFIG. 7. In FIG. 7, two (2) bits (T0-T1) is the frame/type identifier;two (2) bits (R0-R1 (op1)) identifies the response type, e.g., storedone, fetch complete, or attention response, for a first operation;seven (7) bits (Q0-Q6 (op1)) is the Command Queue Tag associated withthe response type of the first operation; two (2) bits (D0-D1 (op1))provides the frame offset code for a first operation (to specify whenfetch data will return with respect to the beginning of the four (4)memory cycle frame); six (6) bits (CRC0-CRC5) is the CRC for the frame;and one bit (ACK) is the acknowledge for the downstream frames (e.g.,acknowledgment for frame in FIG. 5 received by AC). For a store doneresponse type operation, Q0-Q6 denotes the store done tag, whereas for afetch completion response type operation, Q0-Q6 denotes the data tagassociated with fetch data. When the operation is an attention (ATTN)response, one or both command queue tag fields may be overloaded toconvey recovery and status error information back to Host. The responsetype fields R0-R1, the Command Queue fields Q0-Q6 and the frame offsetfields D0-D1 have two operation fields—op1 and op2—and the fields forthe second operation (op2) have the same definition as the fields forthe first operation (op1). To optimize bandwidth, completion informationmay be sent for two operations at a time. Op2 is used to allow the AC toreturn two operations responses per frame (i.e., one store doneoperation and one fetch completion operation, two store done operations,or two fetch completion operations). The response frame sent by the ACchip to the Host when reporting error conditions would be different thenFIG. 7.

Further details of the operation of a memory system, including incertain embodiments distributed memory buffer systems, will bedescribed. FIG. 8 is an exemplary flowchart in accordance with oneembodiment illustrating and describing a method of storing data in amemory system, including a distributed buffer memory system, inaccordance with one embodiment of the present disclosure. While thestoring method 800 is described for the sake of convenience and not withan intent of limiting the disclosure as comprising a series and/or anumber of steps, it is to be understood that the process does not needto be performed as a series of steps and/or the steps do not need to beperformed in the order shown and described with respect to FIG. 8, butthe process may be integrated and/or one or more steps may be performedtogether, simultaneously, or the steps may be performed in the orderdisclosed or in an alternate order.

At 805, a Host (e.g., processor, memory controller, etc.) sends and amemory control circuit, e.g., an AC chip 430, receives a store commandalong with a store data tag from the Host tag pool. The store commandand store data tag is preferably transferred, via a first communicationslink, e.g., link 460 in FIG. 4. The store data tag from the Host tagpool correlates with and identifies the host store command. For ease ofreference, the memory control circuit may be referred to as an ACcircuit or AC chip in this discussion and in FIG. 8. At 810, the Hostsends and the data buffer circuit, e.g., DC circuit, receives data to bestored via a different, second communications link, e.g., link 465 inFIG. 4. For ease of reference, the data buffer circuit may be referredto as a DC circuit or DC chip in this discussion and in FIG. 8. In oneembodiment, no control signal, e.g., address tag, is sent over thecommunication link between the Host and the data buffer circuits. Onlydata in this embodiment is sent over the communication link (e.g., link465 in FIG. 4) between the Host and the data buffer circuits. The datato be stored may be sent to the DC circuit after a configurable (orprogrammable) delay. The delay may be a configurable or programmablefixed delay. By not sending an address tag over link 465, the ability orefficiency of link 465 to transmit data may be increased.

The AC circuit at 815 processes, decodes, or cracks the Host storecommand into a write-to-buffer (“write buffer”) command andstore-from-buffer (“store buffer”) command. At 820, the AC circuit 430may push the store-from-buffer command along with the store data tagreceived from Host into store command FIFO (buffer in the AC scheduler)such that this command can be scheduled later by the scheduler. At 825,the AC circuit 430 sends the write-to-buffer command along with thestore data tag to the DC circuit 440 via a third communications link,e.g., link 470 in FIG. 4. In other words, the store data tag (or Hosttag) sent by the Host for a store command is forwarded to all the DCcircuits from the AC circuit. In this manner, the store data tag sent tothe DC circuits is associated with the command and store data tagreceived from the Host.

In response to and preferably upon receiving the write-to-buffercommand, at 830, the DC circuit 440 pushes incoming data to be storedfrom the second communications link, e.g., link 465 in FIG. 4, into thedata buffer pointed to by the store data tag received from the memorycircuit 430. The DC circuit 440 may push the data into its buffer aftera configurable delay.

At 835, the AC circuit 430 schedules the store-from-buffer command andsends the store command to the memory devices 450 via a fourthcommunications link, e.g., link 480 in FIG. 4. The AC circuit 430 at 840also sends a store-from-buffer command along with store data tag to theDC circuits 440 via the third communications link, e.g., link 470 inFIG. 4. At 845, the DC circuits 440 pull out data to be stored from thedata buffer pointed to by store data tag received from the AC circuit430 via the third communication link, e.g., link 470 in FIG. 4. Thestore data tag is the same store data tag earlier sent to the databuffer circuit when writing data to the data buffer circuit. At 850, theDC circuits 440 send data to be stored to the memory devices 450 via afifth communications link, e.g., link 490 in FIG. 4.

At 855, the AC circuit 430 returns the store data tag to Host via thefirst communications link, e.g., link 460 in FIG. 4. And at 860, theHost returns the store data tag back to the Host tag pool. While FIG. 8discloses and describes the method as a series of steps it will beappreciated that the order described above and in FIG. 8 may be changed.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay be executed substantially concurrently, or the blocks may sometimesbe executed in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustration, and combinations of blocks in the blockdiagrams and/or flowchart illustration, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts or carry out combinations of special purpose hardware and computerinstructions.

Moreover, a system according to various embodiments may include aprocessor and logic integrated with and/or executable by the processor,the logic being configured to perform one or more of the process stepsrecited herein. By integrated with, what is meant is that the processorhas logic embedded therewith as hardware logic, such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), etc. By executable by the processor, what is meant is that thelogic is hardware logic; software logic such as firmware, part of anoperating system, part of an application program; etc., or somecombination of hardware and software logic that is accessible by theprocessor and configured to cause the processor to perform somefunctionality upon execution by the processor. Software logic may bestored on local and/or remote memory of any memory type, as known in theart. Any processor known in the art may be used, such as a softwareprocessor module and/or a hardware processor such as an ASIC, a FPGA, acentral processing unit (CPU), an integrated circuit (IC), a graphicsprocessing unit (GPU), etc.

It will be clear that the various features of the foregoing systemsand/or methodologies may be combined in any way, creating a plurality ofcombinations from the descriptions presented above.

It will be further appreciated that embodiments of the present inventionmay be provided in the form of a service deployed on behalf of acustomer to offer service on demand.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A memory system for storing data in response tocommands received from a Host, the memory system comprising: a memorycontrol circuit to receive commands from the Host and to output modulecommand and control signals; at least one memory device configured tostore data and receive command signals from the memory control circuit;at least one data buffer circuit associated with the at least one memorydevice; a communications link for communicating data between the Hostand the at least one memory device, wherein the communications linkincludes a data communications link between the Host and the at leastone data buffer circuit, and the at least one data buffer circuit andthe at least one memory device, and only data is transmitted on the datacommunications link between the at least one data buffer circuit and theHost; and a control communications link between the memory controlcircuit and the at least one data buffer circuit, wherein the memorycontrol circuit is configured to: in response to receiving the Hoststore command, decode the store command into a write-to-buffer commandand store-from-buffer command; and send the write-to-buffer command anda store data tag to the data buffer circuit over the controlcommunications link, wherein the store data tag specifies the locationto store the data into the at least one data buffer circuit.
 2. Thesystem of claim 1, wherein no store data tag is sent to the at least onedata buffer circuit over the communication link between the Host and theat least one data buffer circuit.
 3. The system of claim 1, wherein theat least one data buffer circuit is configured to: in response toreceiving a write-to-buffer command, push incoming store data into thedata buffer pointed to by the store data tag received from the memorycontrol circuit.
 4. The system of claim 3, wherein the incoming storedata is pushed into the at least one data buffer circuit after aconfigurable delay.
 5. The system of claim 3, wherein the memory controlcircuit is configured to send a store command to the at least one memorydevice, the store command comprising a command and an address locationto store the data in the memory devices.
 6. The system of claim 5,wherein the memory control circuit is further configured to send thestore-from-buffer command along with store data tag to the at least onedata buffer circuit.
 7. The system of claim 6, wherein thestore-from-buffer command and store data tag are sent to the at leastone data buffer circuit over a BCOM link between the memory controlcircuit and the data buffer circuit.
 8. The system of claim 5, whereinthe data buffer circuit is further configured to pull store data fromthe data buffer location pointed to by the store data tag received fromthe memory control circuit over the control communications link and sendthe store data to the at least one memory device.
 9. The memory systemof claim 1, wherein the system further comprises at least one modulehaving the memory circuit formed on a single chip, a group of databuffer circuits formed on separate chips and arranged on the module, anda plurality of memory devices formed as chips and arranged in groups onthe module.
 10. A memory system for reading and writing data to a memorydevice, the system comprising: at least one memory control circuit toreceive commands from a Host and to output command and control signals;at least one memory device configured to read and store data, andreceive command signals from the memory control circuit; at least onedata buffer circuit associated with the at least one memory controlcircuit; a data communications link for communicating data between theHost and the at least one memory device, wherein the data communicationslink includes a communications link between the Host and the at leastone data buffer circuit, and the at least one data buffer circuit andthe at least one memory device, and only data is transmitted on thecommunications link between the at one least data buffer circuit and theHost; and a control communications link between the at least one memorycontrol circuit, the at least one memory device, and the at least onedata buffer circuit for transmitting reading and writing operationsignals of the memory system; wherein the at least one memory controlcircuit is configured to: decode a store command into a write-to-buffercommand and a store-from-buffer command; send the write-to-buffercommand along with the store data tag to the at least one data buffercircuit; send a store command to the at least one memory device; andsend the store-from-buffer command along with store data tag to the atleast one data buffer circuit, and wherein the at least one data buffercircuit is configured to: send incoming store data into a local databuffer pointed to by the local store data tag obtained by the memorycontrol circuit; pull out store data from the local data buffer pointedto by store data tag received from the at least one memory controlcircuit; and send store data to the at least one memory device.
 11. Thesystem of claim 10, wherein the write-to-buffer command and the storedata tag are configured to be sent to the data buffer circuit over thecommunication link between the memory control circuit and the databuffer circuit.
 12. The system of claim 11, wherein the store data tagsent to the at least one data buffer circuit is not sent over the datacommunications link between the Host and the at least one data buffercircuit.
 13. The system of claim 10, configured to send thestore-from-buffer command and store data tag to the data buffer circuitover the link between the memory control circuit and the at least onedata buffer circuit.
 14. The system of claim 13, configured and adaptedso that the at least one data buffer circuit receives its store data tagover the link between the memory control circuit and the at least databuffer circuit, and the store data is sent to the at least one memorydevice from the at least one data buffer circuit via the link betweenthe at least one data buffer circuit and the at least one memory device.